let -> const

we are mutating few lines down

Still in javascript an array can be mutable even if it is const, unless you force the TS compiler with as const at the end so it will not throw a compilation error.

I'd also argue why should we mutate the path? why not having just on immutable path per each page?

i see your point, i guess i could loop thorough it using forEach instead of .map, i will fix it in another PR ...

it's down to code styling, i wouldn't be too strict on that

Another reason why I don't like tailwind

?? elaborate cuz i don't see an issue here

I can foresee even longer class names in the future (even if it does have a cool vs code extension for autocompletion)

These values can be stored as json files.

Why? because it can be useful to leverage other platforms like Localise to handle translation updates